-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using newer client versions in Ducktape tests #24523
base: dev
Are you sure you want to change the base?
Using newer client versions in Ducktape tests #24523
Conversation
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59593#0193b608-bae1-4797-9407-2926e537d9b9:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59593#0193b608-bae7-4220-9aa1-6c822b61a437:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59593#0193b608-bae4-4fb9-ae52-ebb2a488d724:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59593#0193b608-bae5-4166-b6f2-b0b044b04f5d:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59593#0193b5fa-0284-4a84-9539-3ae5db3c0685:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59593#0193b5fa-0287-4e1e-9a5a-49bbe7550e3b:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59601#0193b6a5-6809-43e2-85af-73f7809a4c49:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59601#0193b6a5-6807-45f1-9c31-803c17138aba:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59601#0193b6a5-680c-46e6-b1be-23b9adc47df0:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59601#0193b6a9-b307-4f5b-85b0-afd693f6aed7:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59601#0193b6a9-b30b-4072-8b9e-4c0e81173034:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59601#0193b6a5-680a-42c0-9c21-6b62695414c2:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59601#0193b6a9-b30a-46b1-a496-e4ee860efa56:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59601#0193b6a9-b309-4ba1-9785-34574dabe533:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59644#0193ba9d-ae99-4cc1-bc94-508e6ff014aa:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59644#0193ba9d-ae9a-4deb-a24e-b313cea2a1be:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59644#0193ba9d-ae97-4265-b9d8-88b818819c8e:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59644#0193bab7-e3cb-4d65-a921-9bd92c00dafd:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59644#0193bab7-e3c7-452a-a234-f71b1fb8f58e:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59644#0193bab7-e3c9-40f4-9fd7-d6936bf4b914:
|
Retry command for Build#59593please wait until all jobs are finished before running the slash command
|
aa6ad3c
to
65a3fb4
Compare
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/59601#0193b6a9-b309-4ba1-9785-34574dabe533 |
65a3fb4
to
6b06be5
Compare
6b06be5
to
00ff392
Compare
Retry command for Build#59644please wait until all jobs are finished before running the slash command
|
Is it possible that if we are only using the newest clients, we may start releasing code that causes issues with older clients? I guess to maybe put it another way, does this bias our implementations and testing to ignore older clients? |
This question ca be asked both sides, i.e. do we ignore new clients while using the older ones ? We can and probably we should add basic tests that will sweep through the client versions and test some basic features. |
Definitely not opposed to updating our test clients - absolutely should do that. I wonder if, when a client is selected, we randomly select a version to use rather than always using the most recent one? |
Signed-off-by: Michał Maślanka <michal@redpanda.com>
Signed-off-by: Michał Maślanka <michal@redpanda.com>
Now, with the new Kafka tools the producer is by default using idempotent produce requests. This creates an id allocator topic which archival handles differently than usual kafka topics. Signed-off-by: Michał Maślanka <michal@redpanda.com>
The new version of Kafka CLI outputs additional log lines on error. We need to skip them to correctly parse the result. Signed-off-by: Michał Maślanka <michal@redpanda.com>
transactions are are required for idempotent producers to work correctly. Signed-off-by: Michał Maślanka <michal@redpanda.com>
The schema registry client caches the schemas, recreating client drops the caches and force it to request information from the registry. Signed-off-by: Michał Maślanka <michal@redpanda.com>
Signed-off-by: Michał Maślanka <michal@redpanda.com>
Signed-off-by: Michał Maślanka <michal@redpanda.com>
00ff392
to
aed11cd
Compare
Signed-off-by: Michał Maślanka <michal@redpanda.com>
/ci-repeat 1 |
Retry command for Build#59864please wait until all jobs are finished before running the slash command
|
CI test resultstest results on build#59864
|
Updated Kafka tools and librdkafka to the new versions in our test environments.
Backports Required
Release Notes